-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add x25519 Support #88
base: master
Are you sure you want to change the base?
Add x25519 Support #88
Conversation
@TJKoury |
Great! I need x25519 support as well, for ECDH. |
To clarify: I'm aware that you can actually use Ed25519 for ECDH, but most heavily used libraries follow the separation of using Ed25519 for 'sign' & 'verify', and x25519 for 'deriveBits' & 'deriveKey' for ECDH_ES, including Node. Seeing as how all the examples are testing using the Node API, and hopefully the WebCrypto browser standards will follow the Node example, implementing x25519 for completeness seems appropriate for an isomorphic library to bring the browser up to Node's capabilities. |
So, thoughts? |
Bump |
2 similar comments
Bump |
Bump |
Since integration of the ECDH_ES mech is waiting on this issue, and I need x25519 for a project, I integrated a different crypto library for the time being.
Seems to be passing the test suite copied from the ED mech, though I am certain I missed something.
Standing by for feedback.